Automatically fold inactive regions - #14796

Manual folds incorrectly suppress later automatic folding

Extension/​src/​LanguageServer/​client.ts:3018

A manual fold also marks the editor as already auto-folded. If the user manually folds, unfolds, and then enables autoFoldInactiveRegions, the settings-change path will refuse to auto-fold this editor even though no automatic fold occurred. Only record the editor when autoFold is actually true.

Route document command using the current editor URI

Extension/​src/​LanguageServer/​extension.ts:931

Route this document-scoped command from the current editor URI. ClientCollection.didChangeActiveEditor updates ActiveClient only after awaiting the new client's editor-change notification, so invoking this command during a multi-root editor switch can add the pending fold to the previous client; the actual owner receives the ranges and never fulfills that request.

Track pending folding operations per editor, not document URI

Extension/​src/​LanguageServer/​client.ts:3005

Pending manual operations are keyed only by document URI, although folding state is per TextEditor. If the same document is open in two editor groups and the user requests a fold before results are complete, switching to the other view causes tryApplyInactiveRegionFolding to consume the request there; the original view remains unfolded (and a request from the second view can overwrite the first). Track pending operations by editor instance (for example, a WeakMap<vscode.TextEditor, ...>) and consume only the operation belonging to the active editor.

Mark empty-result editors as auto-folded

Extension/​src/​LanguageServer/​client.ts:3034

Mark the editor as auto-folded before returning for an empty complete result. Otherwise, a file opened with no inactive branches remains absent from autoFoldedEditors, so a later edit that introduces an inactive branch triggers automatic folding even though automatic folding is documented to happen on open and only once per editor instance.

Retry automatic folding when code folding is enabled later

Extension/​src/​LanguageServer/​client.ts:1911

Re-evaluate automatic folding when codeFolding changes too. If a file is opened while autoFoldInactiveRegions is true but code folding is disabled, enabling code folding later leaves the active editor unfolded because the cached complete ranges are never retried (and the outgoing inactive-range flag was already enabled by autoFoldInactiveRegions, so this setting change need not produce another IntelliSense result).

Refresh inactive-region decorations when dimInactiveRegions changes

Extension/​src/​LanguageServer/​client.ts:1914

With codeFolding enabled (the default), the native dimInactiveRegions flag now remains true even when the user toggles dimming. This settings-change path does not update inactive-region decorations for dimInactiveRegions, so an already-open editor can retain stale dimming (or fail to gain it) until another IntelliSense result happens to arrive. Handle dimInactiveRegions changes here by immediately disposing or rebuilding decorations from the cached ranges while keeping native range reporting enabled independently.